Repository navigation
Publish Fullbleed support page with pending sponsorship status - #8
Merged
Merged
Conversation
krflol
changed the title
krflol
marked this pull request as ready for review
October 2, 2026 13:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository README now links to
/support/, which currently returns 404. Publish that destination with useful ways to try Fullbleed, report reproducible problems, contribute examples, and improve the documentation.GitHub Sponsors is still awaiting approval. The page explicitly says sponsorship is not yet available and has no donation checkout link. It keeps the MIT license and commercial-use terms clear and identifies the maintainer who will receive optional support once the profile is public. Navigation, the home page, and the footer link to this page.
Validation: strict MkDocs build, all 51 built pages' internal links and anchors, and desktop/mobile browser checks. The branch includes current main, including the verified 2.5.5 playground; local documentation checks reuse its unchanged generated assets, and CI rebuilds them independently.